Archives and Access Rights

I have a project that I would like to share with external users that have their own database. They do not have the ability to access our database. We're trying to figure out how to restrict their access to some of the data in the project. We were attempting to do this with access rights, but it appears when you restore a project in a database that does not have the same users and groups as the originating database, the project restores giving Everyone complete access to the data. So I guess my question is, am I doing something wrong when I'm creating the archive? If not, is there some way to do what I'm looking to do easily, restrict the receiving user from seeing some of the data? Or will I need to remove said data from a copy of the modules and THEN create the archive? Thanks in advance for any help.
mvenos - Tue Aug 10 11:02:49 EDT 2010

Re: Archives and Access Rights
llandale - Wed Aug 11 08:56:38 EDT 2010

As for restoring projects with rights: in the old days when an archived project provided user with ID "1e4" RMCD rights, then which ever user in the restored database with ID 1E4 (if any) would get those rights. That makes no sense. DOORS v8 now just erases all the specific rights when a project or module is archived.

To share data like this you should want to use Partitions. Create a partition in your database of your project, locking down certain data as appropriate. Create and send the partition. You cannnot edit any data in that project because its in a sent partition. The away folks can edit much of the data, but not the data you locked down.

  • Louie

Re: Archives and Access Rights
mvenos - Thu Aug 12 15:08:37 EDT 2010

llandale - Wed Aug 11 08:56:38 EDT 2010
As for restoring projects with rights: in the old days when an archived project provided user with ID "1e4" RMCD rights, then which ever user in the restored database with ID 1E4 (if any) would get those rights. That makes no sense. DOORS v8 now just erases all the specific rights when a project or module is archived.

To share data like this you should want to use Partitions. Create a partition in your database of your project, locking down certain data as appropriate. Create and send the partition. You cannnot edit any data in that project because its in a sent partition. The away folks can edit much of the data, but not the data you locked down.

  • Louie

Thanks for the response. It looks like Partitioning is the way to go.